Systems and methods of package container return

ABSTRACT

A package container includes a body, a cover, a cover lock, a user interface, and an electronic controller. The electronic controller includes a memory and a processor. The processor is configured to store order information in the memory. The order information indicates that the package container is assigned to transport one or more items. The processor is configured to detect, at a first time, that the cover has moved from a closed state to an open state. The processor is also configured to store a trial start time that is based on the first time. The processor is configured to, based at least in part on receiving a return request via the user interface and detecting that the cover is in the closed state, store a second time as a trial end time and send a transportation request to a delivery management server to initiate transportation of the package container.

FIELD

This disclosure relates generally to intelligent package containers thatcan be used to return items.

BACKGROUND

In recent years, consumers have been purchasing more products on-line.Consumers often have a return window starting from a delivery dateduring which items purchased on-line can be returned for a refund. Someconsumers open the package soon after the package is delivered. Otherconsumers may be unavailable (e.g., busy or travelling) and do not openthe package for days after delivery of the package. The return window isgenerally kept long enough (e.g., 2 weeks) so that more consumers havetime to try out the items. Having such a long return window increases alikelihood of some consumers using the items during the return windowand then returning the used items for a refund. Further, the items thatwill be returned are unavailable during the long return window forreselling to other consumers. Shortening the return window can makeonline shopping inconvenient for busy people who might not have time totry out an item before the shorter return window expires.

SUMMARY

This disclosure provides a package container that enables determining atrial start time based on when the package container is opened afterdelivery. The package container enables return windows (e.g., trialperiods) to be based on opening of the package rather than an order dateor a delivery date. For example, the package container includes a body,a cover, a cover lock, a user interface, and an electronic controller.The body includes a base, an opening, and at least one side wall. Thebase, the opening, and the at least one side wall all define a cavitytherebetween. The cover is coupled to the body. The cover is movablefrom a closed state covering the opening to an open state. The coverlock, when activated, keeps the cover in the closed state. Theelectronic controller is electrically coupled to the cover lock and tothe user interface. The electronic controller includes a memory and aprocessor. The memory is configured to store package informationindicating that the package container is assigned to transport an itemin the cavity. The processor is configured to, based at least in part ondetecting at a first time that the cover has moved from the closed stateto the open state, store the first time as a trial start time of theitem in the memory. The processor is configured to store a second timeas a trial end time in the memory.

Since a trial starts after a package container is opened, shorter trialperiods (e.g., 2 hours) give consumers time to try out the itemsregardless of whether the package container is opened soon afterdelivery or days after delivery. The shorter trial period (e.g., 2hours) reduces a likelihood of a consumer using an item (e.g., wearing ajacket to a party) before returning the item. Returns have to berequested within the shorter trial period in order to qualify for arefund (e.g., a full refund). For consumers who open the packagecontainer soon after delivery, any items that are to be returned arereturned within the shorter trial period (e.g., 2 hours) and becomeavailable early (e.g., sooner than for a two week return window) forreselling to other consumers. The package container can also enableconvenient returns. In some examples, the package container initiates,based on a trial start time, display of a reminder indicating anavailable time to initiate a return of an item. In a particular example,a user can activate a button (e.g., the user interface) of the packagecontainer to request a return, place the item in the package container,close the cover of the package container, and place the packagecontainer outside for pickup. In this example, the package container,based at least in part on receiving the return request, activates thecover lock of the package container, stores a second time as a trial endtime and sends a transportation request to initiate transportation ofthe package container. In a particular example, the package containerdetermines a trial duration based on a comparison of the trial starttime and the trial end time, and selectively sends the transportationrequest in response to determining that the trial duration is less thanor equal to a return window.

The package container can enable implementation of dynamic policies,such as return policies, trial length policies, and/or policies based onitem condition, to incentivize consumers (e.g., buyers) to have greaterbrand loyalty. For example, responsive to receiving a return request viathe package container, a dynamic policy can be activated. To illustrate,the user may be offered an extension to the return window to try out theitem for a longer duration, an incentive (e.g., a partial refund, adiscount on a future purchase, reward points, or a combination thereof)to keep the item. The offer may be displayed on an interface of thepackage container, a display of a user device, or both. In someexamples, the offer is based on a condition of the item or a type ofitem. To illustrate, a greater incentive may be offered to keep adamaged or perishable item as compared to an undamaged or non-perishableitem. In some examples, the package container enables implementation ofuser-specific policies, such as policies based on a relationship of theuser (e.g., the customer) to a seller (e.g., retailer) of the item. Toillustrate, a longer return window, a greater incentive to keep theitem, or a longer extension to the return window is offered to membersof a loyalty program. The package container can be used for returns oftime-based rental items, such as shoes, clothes, party supplies, tools,etc. In some examples, the package container can be used for timingreturns of a time-based service (e.g., a monthly service or a quarterlyservice), such as a try and buy service for clothing, shoes, purses,etc. In some examples, the order is placed by a user for delivery (e.g.,of a gift) to someone other than the user. To illustrate, the packagecontainer may be delivered to a recipient who is different from the userwho placed the order. The package container enables a recipient toreturn one or more received items. For example, the recipient can use apackage container to return one or more items received in the samepackage container, another package container, or multiple packagecontainers.

Other aspects of the disclosure will become apparent by consideration ofthe detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a package container in an open state, inaccordance with some embodiments.

FIG. 2 is a ladder diagram of examples of communications of the packagecontainer of FIG. 1.

FIG. 3 is a ladder diagram of examples of communications of the packagecontainer of FIG. 1.

FIG. 4 is a ladder diagram of examples of communications of the packagecontainer of FIG. 1.

FIG. 5 is a diagram of a package container, in accordance with someembodiments.

FIG. 6 is a flowchart of a method of using the package container of FIG.1 to return an item, in accordance with some embodiments.

DETAILED DESCRIPTION

For ease of description, each of the exemplary systems presented hereinis illustrated with a single exemplar of each of its component parts.Some examples may not describe or illustrate all components of thesystems. Other exemplary embodiments may include more or fewer of eachof the illustrated components, may combine some components, or mayinclude additional or alternative components. Particular embodiments aredescribed with reference to the drawings. In the description, commonfeatures are designated by common reference numbers throughout thedrawings.

FIG. 1 is a diagram of one exemplary embodiment of a package container100 in an open state. The package container 100 includes a body 105, acover 110, a cover lock 115, a first locking bar 120, a second lockingbar 125, a user interface 112, and an electronic controller 130. Thepackage container 100 described herein may include fewer, additional, ordifferent components in different configurations than the packagecontainer 100 illustrated in FIG. 1. For example, in some embodiments,the package container 100 includes only one locking bar.

The body 105 is generally box-shaped. The body 105 includes, among otherthings, an opening 135, a base 140, a front 145, a back 150, a firstside 155, and a second side. The second side is opposite from the firstside 155. The opening 135, the base 140, the front 145, the back 150,the first side 155, and the second side define a cavity 165. The cavity165 holds the item or items being transported. As an illustrativeexample, an item 170 is placed within the cavity 165 in FIG. 1. In someexamples, multiple items are placed within the cavity 165. In someexamples, one or more packages including one or more items are placedwithin the cavity 165. In alternate embodiments, the body 105 may have agenerally cylindrical shape (not shown) defined by an opening, a base,and at least one side wall defining a cavity therebetween and coverablewith a cover. Other configurations of the body 105 are also suitable solong as they define a cavity for placement of packages, parcels, andother items.

In the embodiment illustrated in FIG. 1, the cover 110 is pivotablycoupled to the body 105 via one or more hinges 175. In otherembodiments, the cover 110 is coupled to the body 105 via other types ofconnectors (for example, sliding connectors). In an open state(illustrated in FIG. 1), the cover 110 is positioned away from theopening 135 such that the cavity 165 is exposed and the contents withinthe cavity 165 are accessible. In a closed state, the cover 110 ispositioned adjacent to the opening 135 such that cavity 165 is securedand the contents within the cavity 165 are not accessible.

The electronic controller 130 includes a container manager 132 (e.g., aprocessor) to control the package container 100. The electroniccontroller 130 includes memory 134 configured to store packageinformation, order information, delivery information, trial information,item information, or a combination thereof.

The cover lock 115 is positionable in an unlocked state (illustratedFIG. 1) or a locked state (not illustrated). When the cover 110 is inthe closed state and the cover lock 115 is activated (e.g., is in thelocked state), the cover lock 115 engages a hook 180 included in thecover 110 to prevent the cover 110 from changing to the open state.Alternatively, when the cover lock 115 is deactivated (e.g., is in theunlocked state), the cover 110 may freely move between the closed stateand the open state. The cover lock 115 is electrically coupled to theelectronic controller 130. The container manager 132 adjusts the coverlock 115 between the locked and unlocked states by generating andsending control signals to the cover lock 115. In some implementations,the cover 110 includes a membrane and the package container 100 includesa closing mechanism (e.g., an actuator) that self-tightens the membranearound the item 170. In these implementations, the cover 110 isconsidered to be in a closed state when the membrane is in a tightenedstate around the item 170. The cover lock 115 is configured, whenactivated, to prevent the membrane from changing from the tightenedstate.

Upon being delivered to its destination, the package container 100 canbe securely attached to a fixed anchor point via one or more securingmechanisms included in the package container 100. In some embodiments,the securing mechanism includes the first locking bar 120 and the secondlocking bar 125, as illustrated in FIG. 1. In some embodiments, thefixed anchor point is a bar that is attached, for example, to a spot onthe ground outside the house of the recipient of the package container100. The package container 100 remains securely attached to the fixedanchor point until the recipient of the package container 100 retrievesthe contents placed within the cavity 165 of the package container 100,as described in further detail below.

In some examples, the package container 100 includes a transceiver. Theuser interface 112, the transceiver, or both, are operably coupled tothe electronic controller 130 to control, for example, the states of thecover lock 115, the first locking bar 120, and the second locking bar125. In some embodiments, the container manager 132 receives an unlockcode from a user via the user interface 112 (or via the transceiver) anddeactivates (e.g., changes the state of) the cover lock 115, the firstlocking bar 120, or the second locking bar 125. For example, thecontainer manager 132 changes the cover lock 115 from the locked stateto the unlocked state in response to receiving an unlock code from therecipient via the user interface 112, from the recipient via thetransceiver, or from a delivery management server via the transceiver.Alternatively or in addition, the container manager 132 deactivates(e.g., unlocks) the cover lock 115 in response to performing a biometricvalidation. For example, the container manager 132 validates afingerprint obtained by the user interface 112 (or received via thetransceiver). The container manager 132 stores a trial start time in thememory 134 in response to deactivating the cover lock 115, detectingthat the cover 110 has transitioned from the closed state to the openstate for the first time subsequent to deactivation of the cover lock115, or both.

In some examples, the user interface 112 is used to request a return ofthe item 170. In a particular example, the user interface 112 includes abutton that is activated (e.g., pressed) by a user to request return ofthe package container 100. The container manager 132, based at least inpart on receiving a return request via the user interface 112 (e.g.,detecting an activation of the button), initiates provision of returninformation (e.g., return instructions) to the user, activates the coverlock 115, requests pickup of the package container 100, stores a trialend time in the memory 134, or a combination thereof, as furtherdescribed with reference to FIGS. 2-4. The package container 100 can beretrieved by an authorized party (for example, a delivery person of ashipping company).

FIGS. 2-4 provide illustrative examples of operations at andcommunications between the package container 100, a user device 250, anda delivery management server 252. In other examples, fewercommunications, additional communications, different communications,communications in a different order, or a combination thereof, occurbetween the package container 100, the user device 250, and the deliverymanagement server 252. It should be understood that one or moreoperations described herein as performed by the package container 100are performed by the container manager 132.

The delivery management server 252 is illustrated in FIGS. 2-4 as asingle server for ease of description. In other examples, the deliverymanagement server 252 refers to a delivery management system thatincludes multiple devices. In some examples, the delivery managementsystem includes devices associated with multiple entities, such as amanufacturer, a seller, a retailer, a delivery company, or a combinationthereof. In some examples, some of the communications described withreference to the delivery management server 252 refer to communicationswith servers of a first entity (e.g., the retailer) and somecommunications described with reference to the delivery managementserver 252 refer to communications with servers of a second entity(e.g., the delivery company).

The user device 250 is illustrated in FIGS. 2-4 as a single device forease of description. In some examples, the user device 250 correspondsto multiple devices. For example, some of the communications describedwith reference to the user device 250 refer to communications with oneor more devices of a buyer associated with (e.g., a user that placed)the order. In a particular example, some of the communications describedwith reference to the user device 250 refer to communications with oneor more devices of a recipient of the package container 100. In someexamples, the recipient differs from an intended recipient associatedwith the order, e.g., due to delivery errors. The user device 250includes one or more of a mobile device, a communication device, acomputer, a wi-fi network component, an internet of things device, or asmart watch. In a particular aspect, the user device 250 includes theuser interface 112 and the user interface 112 is not a physicallyattached component of the package container 100. The user interface 112is communicatively coupled to the package container 100. For example,the package container 100 is configured to communicate, via atransceiver, with the user interface 112. In some implementations, auser can activate the user interface 112 by selecting an optiondisplayed by the user device 250 to request a return of the item 170.

Each of the examples illustrated in FIGS. 2-4 includes examples ofcommunications and operations during an order stage 206, a shipmentstage 208, a trial stage 210, and a return stage 212. During the orderstage 206, a user places an order and, responsive to the order, one ormore items (e.g., clothes, books, shoes, grocery, cosmetics, homemedical tests, dry cleaning, etc.) are placed in a package container100, e.g., by a seller or a retailer. In some examples, the deliverymanagement server 252 selects a particular warehouse based on proximityto a delivery destination and forwards the order to the particularwarehouse. An employee at the particular warehouse, in response toreceiving the order, places the item 170 in the package container 100.In some examples, the delivery management server 252 determines that theitem 170 located in a package container 100 that is being returned fromanother user. In these examples, the delivery management server 252updates package information (e.g., order information, user information,account information, destination information, or a combination thereof)associated with the package container 100 to indicate that the packagecontainer 100 is to be shipped to the destination indicated in theorder. In some examples, a package container 100 containing an item 170being returned from one house can be routed to another house in the samestreet, the same neighborhood, the same city, the same state, or acombination thereof, without an intermediate stop at a warehouse toremove the item 170 from a first package container, to designate theitem 170 as available for selling or rental, and to place the item 170in a second package container.

During the shipment stage 208, the package container 100 is transported,e.g., from a warehouse or a previous delivery destination, to a deliverylocation (e.g., the destination indicated in the order or an incorrectdestination). During the trial stage 210, a trial of the ordered itemsbegins. For example, the trial begins at a time at which the cover lock115 is deactivated, the cover 110 transitions from a closed state to anopen state for the first time subsequent to deactivation of the coverlock 115, or both. During the return stage 212, the user initiates areturn of the item 170, the trial ends, and the package container 100 isretrieved from the user.

In a particular aspect, the item 170 is returned in a second packagecontainer that is different from a first package container used todeliver the item 170. For example, multiple package containers may bedelivered to the delivery location. A user may retrieve the item 170from the first package container and initiate return of the item 170using the second package container. In a particular aspect, the user mayuse the second container to initiate return of one or more additionalitems received in one or more package containers. In this example, atrial of the item 170 begins when the cover lock 115 of the firstpackage container is deactivated, when the cover 110 of the firstpackage container transitions from a closed state to an open state forthe first time subsequent to deactivation of the cover lock 115, orboth. The user places one or more return items (e.g., the item 170, theadditional items, or a combination thereof) in the second packagecontainer. The user provides identifiers of the return items, e.g., viathe user interface 112 or a transceiver of the second package container,to indicate that the return items are being returned in the secondpackage container. In a particular aspect, one or more sensors (e.g., acamera) of the second package container provides an input indicatingidentifiers of the return items.

In a particular implementation, the user device 250, in response toreceiving an input (e.g., a user input, a sensor input, or both)indicating that the return items are being returned in the secondpackage container, sends a notification indicating the input to thedelivery management server 252. In a particular aspect, the deliverymanagement server 252, responsive to receiving the input identifies theorders, the retailers, the package containers, or a combination thereof,associated with the return items. For example, the delivery managementserver 252, responsive to receiving the input from the second packagecontainer and determining that the input indicates an identifier of theitem 170, determines that the second package container is being used toreturn the item 170 that is associated with a particular order, thefirst package container, or both. In this implementation, the deliverymanagement server 252, in response to receiving the notification, sendspackage information to the second package container. In an alternativeimplementation, the second package container receives the packageinformation via the user interface 112.

The package information indicates that the second package container isassigned to transport the return items associated with correspondingorders. For example, the package information indicates that the secondpackage container is assigned to transport the item 170 associated withthe particular order. In a particular aspect, the package informationincludes order information, delivery information, trial information, ora combination thereof, associated with the orders and the packagecontainers associated with the return items. For example, the packageinformation indicates a trial start time associated with the firstpackage container, a return window associated with the particular order,or both.

The trials for the return items end when the cover 110 of the secondpackage container transitions from the open state to the closed statefor the last time prior to the cover lock 115 being activated, when thecover lock 115 is activated, when the return of the second packagecontainer is initiated, when the second package container is picked upfrom the delivery location, or a combination thereof. In a particularaspect, the return items are associated with multiple retailers. Forexample, the item 170 and a second return item are associated with afirst retailer and a second retailer, respectively. In a particularimplementation, the return items are post-processed by return servicesof the multiple retailers. For example, the item 170 and the secondreturn item are post-processed by a first return service of the firstretailer and a second return service of the second retailer,respectively. In a particular implementation, a third-party serviceretrieves the return items from the second package container and sortsout disposition of the return items.

In an example 200 illustrated in FIG. 2, the package container 100 haslimited capabilities and most actions of the container manager 132 aredirected by the delivery management server 252. During the order stage206, the user device 250, in response to receiving user input, sendsorder information 201 to the delivery management server 252. The orderinformation 201 indicates an order identifier, user account information,a delivery destination, identifiers of one or more ordered items, anintended recipient identifier, or a combination thereof. For example,the order information 201 indicates that an order has been placed by theuser for the ordered items to be delivered to an intended recipient atthe delivery destination. The intended recipient may be the same as ordifferent from the user.

The delivery management server 252, in response to receiving the orderinformation 201, initiates placement of items (e.g., merchandise) in thepackage container 100. For example, the delivery management server 252sends an order notification to a warehouse in response to receiving theorder information 201. The order notification indicates an ordered itemidentifier, the order identifier, or both. An employee (or a robot) ofthe warehouse places the item 170 in the package container 100responsive to the order notification. In some examples, the item 170 isdifferent from the ordered item, e.g., due to a packing error.

In a particular implementation, the employee (or the robot) sends apacking notification to the delivery management server 252 indicatingthat the ordered item associated with the order has been placed in thepackage container 100 and that the package container 100 is ready forshipping. For example, the packing notification includes the ordereditem identifier, a container identifier of the package container 100,the order identifier, or a combination thereof. The delivery managementserver 252, in response to receiving the packing notification, sends aclose lid command 203 to the package container 100.

In a particular aspect, the delivery management server 252, in responseto receiving the packing notification, sends package information to thepackage container 100. In an alternative aspect, the package container100 receives the package information via the user interface 112. Thecontainer manager 132 stores the package information in the memory 134.The package information indicates that the package container 100 isassigned to transport the ordered item (e.g., the item 170) associatedwith the order.

The container manager 132, in response to receiving the close lidcommand 203 and determining that the cover 110 is in an open state,sends a command (e.g., to activate a motor or the hinges 175) to closethe cover 110. The package container 100, in response to detecting thatthe cover 110 is in the closed state subsequent to receiving the closelid command 203, sends a closed notification 205 to the deliverymanagement server 252.

In an alternative implementation, the cover 110 is physically closed,e.g., by the employee or the robot (instead of the close lid command 203being sent from the delivery management server 252). In thisimplementation, the package container 100 sends the closed notification205 to the delivery management server 252 in response to detecting thatthe cover 110 is in the closed state, receiving a user input via theuser interface 112, or both.

The delivery management server 252, in response to receiving the closednotification 205, sends a lock command 207 to the package container 100.In a particular aspect, the delivery management server 252, in responseto receiving the closed notification 205, updates an order statusindicating that at least one item of the order is ready for shipping.The container manager 132 activates the cover lock 115 in response toreceiving the lock command 207. In FIG. 2, the cover lock 115 isactivated/deactivated based on commands received from the deliverymanagement server 252. The package container 100 is considered to belocated at a merchant location (e.g., a warehouse of a seller, awarehouse of a retailer, a warehouse of a delivery company, a store, adelivery vehicle, an anchor point, or a combination thereof) prior toreceiving the lock command 207.

During the shipment stage 208, the package container 100 is shipped to adelivery location. For example, the package container 100 is transportedto a delivery destination indicated in the order information 201. Thepackage container 100, in response to detecting arrival at the deliverylocation, sends a delivery notification 209 to the delivery managementserver 252. The package container 100 detects arrival at the deliverylocation in response to receiving location information (e.g., globalpositioning system (GPS) information or an anchor point identifier)indicating that the package container 100 has arrived at the deliverydestination, receiving a user input via the user interface 112 (or atransceiver) indicating that the package container 100 has beendelivered, or both. The package container 100 is considered to be intransit between receiving the lock command 207 and sending the deliverynotification 209.

In a particular aspect, the delivery management server 252, in responseto receiving the delivery notification 209, updates an order statusindicating that the ordered item (e.g., the item 170) has beendelivered. In a particular aspect, the delivery management server 252,in response to receiving the delivery notification 209 from thecontainer manager 132, sends the delivery notification 209 to the userdevice 250 (e.g., a device of the buyer, a device of the intendedrecipient, or both). For example, the delivery management server 252sends, to the user device 250, the order status indicating that theordered item has been delivered. In FIG. 2, the package container 100initiates sending of the delivery notification 209 to the user device250 by sending the delivery notification 209 to the delivery managementserver 252.

During the trial stage 210 (e.g., when a recipient is ready for trialsubsequent to receiving the package container 100), the recipient sendsan unlock request 213 via (e.g., an on-line shopping application of) adevice of the recipient (e.g., the user device 250) to the deliverymanagement server 252. In a particular aspect, the unlock request 213includes the container identifier, credentials (e.g., a username, apassword, biometric information, or a combination thereof) of therecipient, or a combination thereof.

The delivery management server 252, in response to receiving the unlockrequest 213 and authenticating the recipient, sends an unlock command215 to the container manager 132. In a particular aspect, the deliverymanagement server 252 identifies the order associated with the containeridentifier, authenticates the recipient in response to determining thatthe credentials match authentication information associated with theintended recipient, and sends the unlock command 215 in response toauthenticating the recipient.

The container manager 132 deactivates the cover lock 115 in response toreceiving the unlock command 215 from the delivery management server252. In a particular aspect, the container manager 132, in response todeactivating the cover lock 115, updates the user interface 112 toindicate that the cover lock 115 is deactivated. In a particular aspect,the cover lock 115 generates a sound, a light, or both, whiletransitioning from a locked state to an unlocked state. In this aspect,the recipient determines that the cover lock 115 is deactivated inresponse to detecting the sound, the light, or both.

In a particular implementation, the recipient sends an open lid command217 via the online shipping application of the recipient's device (e.g.,the user device 250) to the container manager 132. The container manager132, in response to receiving the open lid command 217, determining thatthe cover lock 115 is deactivated, and determining that the cover 110 isin a closed state, sends a command (e.g., to activate a motor or thehinges 175) to open the cover 110. In an alternative implementation, thecover 110 is physically opened, e.g., by the recipient (instead of theopen lid command 217 being sent from the user device 250).

The container manager 132 detects at an opened time that the cover 110has moved from the closed state to the open state. The container manager132, in response to detecting that the cover 110 has moved from theclosed state to the open state for the first time subsequent toreceiving the unlock command 215, sends an opened notification 219 tothe delivery management server 252, stores the opened time as a trialstart time in the memory 134, or both. In a particular aspect, a trialof the ordered item (e.g., the item 170) starts at the trial start time.The delivery management server 252, in response to receiving the openednotification 219, sends a trial start notification 221 to the userdevice 250 (e.g., a device of the recipient, a device of the buyer, orboth). The package container 100 thus initiates sending of the trialstart notification 221 to the user device 250 by sending the openednotification 219 to the delivery management server 252. In a particularaspect, the delivery management server 252 stores a server trial starttime based on an unlock request time at which the unlock request 213 isreceived from the user device 250, an unlock command time at which theunlock command 215 is sent to the package container 100, an opened timeat which the opened notification 219 is received from the packagecontainer 100, a trial notification time at which the trial startnotification 221 is sent to the user device 250, or a combinationthereof.

In a particular aspect, the user device 250 displays the trial startnotification 221. For example, the user device 250 provides the trialstart notification 221 to a display. The trial start notification 221indicates that a trial of the ordered item (e.g., the item 170) hasstarted. In a particular example, the trial start notification 221indicates terms and conditions of the trial. To illustrate, the trialstart notification 221 indicates that a return has to be requested by aparticular time (e.g., 2 hours or 1 day) to get a particular refund(e.g., 100% or 50%).

In a particular aspect, the container manager 132 determines a remindertime based on the trial start time (e.g., 10:00 AM). For example, atrial duration threshold (e.g., 2 hours) indicates a size of a returnwindow. The container manager 132 determines the reminder time based onthe trial start time and the trial duration threshold (e.g., remindertime=trial start time+0.75 (trial duration threshold)). The containermanager 132 generates a reminder indicating an available time (e.g.,available time=0.25 (trial duration threshold)) to initiate a return ofthe item 170. The container manager 132 initiates display of thereminder based on the reminder time. For example, the container manager132 provides the reminder to the user interface 112, the user device250, or both, for display. In a particular aspect, the deliverymanagement server 252 determines a second reminder time based on thetrial start time and the trial duration threshold, generates a secondreminder indicating an available time to return the item 170, andinitiates display of the second reminder at the second reminder time.For example, the delivery management server 252 provides the secondreminder to the user interface 112, the user device 250, or both fordisplay. In some examples, the reminder time (and the available timeindicated by the reminder) is different from the second reminder time(and the available time indicated by the second reminder). In aparticular aspect, the container manager 132, the delivery managementserver 252, or both, initiate a display of a reminder in response todetermining that the package container 100 has not been opened (e.g.,the cover 110 has not transitioned from a closed state to an open state)within a threshold duration of delivery of the package container 100.

The recipient may decide that the item 170 is to be returned for variousreasons, such as the item 170 is different from the ordered item or theitem 170 is the ordered item but the recipient does not want to keep theitem 170 after seeing or trying out the item 170. During the returnstage 212, the recipient initiates return of the item 170 by sending areturn request 222 via the user interface 112 to the package container100. In a particular aspect, the user interface 112 includes a button onthe package container 100 and the recipient presses the button toinitiate the return. In some examples, the package container 100includes a button cover to prevent the button from being accidentlypressed, e.g., during transportation of the package container 100. Therecipient moves (e.g., lifts) the button cover to access the button andpresses the button to initiate the return. It should be understood thata button is provided as an illustrative example. In some examples, theuser interface 112 includes a touch screen, a lever, a microphone, orother input devices and the package container 100 includes an interfacecover that prevents accidental access to at least a portion (e.g., thetouch screen, the lever, the microphone, or other input device) of theuser interface 112. In a particular aspect, at least a portion (e.g., abutton, a touch screen, a lever, a microphone, or other input device) ofthe user interface 112 is located at an exterior surface (e.g., outersurface) of at least one of the cover 110 or the body 105. In aparticular aspect, at least a portion (e.g., a button, a touch screen, alever, a microphone, or other input device) of the user interface 112 isaccessible while the cover 110 is in an open state and is inaccessiblewhile the cover 110 is in a closed state. In a particular aspect, atleast a portion (e.g., a button, a touch screen, a lever, a microphone,or other input device) of the user interface 112 is disabled subsequentto expiration of the return window.

Returning to the return stage 212, the container manager 132 generates areturn request notification 223 in response to receiving the returnrequest 222 from the user interface 112. In a particular aspect, thecontainer manager 132 sends a confirmation request to the user device250 in response to receiving the return request 222. The user device 250receives a user input responsive to displaying the confirmation requestand sends the user input to the container manager 132. In this aspect,the container manager 132 generates the return request notification 223in response to determining that the user input indicates a confirmationthat return is requested. In a particular aspect, the user interface 112requests the recipient to indicate recipient return information, such asthe ordered item, the item to be returned, the order number, a reasonfor returning the item, or a combination thereof. In this aspect, thecontainer manager 132, in response to receiving user input indicatingthe recipient return information (e.g., the ordered item identifier, anitem identifier of the item 170, the order identifier, a reason, or acombination thereof), generates the return request notification 223indicating the recipient return information. In a particular aspect, thereturn request notification 223 indicates the container identifier ofthe package container 100. The container manager 132 sends the returnrequest notification 223 to the delivery management server 252. In aparticular aspect, the container manager 132 stores a request time inthe memory 134. The request time is based on a time at which the returnrequest 222 is received by the container manager 132.

In a particular aspect, the user device 250 generates the return requestnotification 223 in response to receiving a user input indicating thereturn request 222. In a particular aspect, the container manager 132,responsive to receiving the return request 222, refrains from requestingthe recipient to provide recipient return information. In this aspect,the delivery management server 252, in response to receiving the returnrequest notification 223, sends a request for the recipient returninformation to the user device 250, the package container 100, or both.The user device 250 (or the package container 100) displays the requestfor the recipient return information, receives user input indicating therecipient return information, and sends the recipient return informationto the delivery management server 252. The recipient return informationincludes an ordered item identifier, an item identifier of the item 170,the order identifier, a reason for returning the item 170, a containeridentifier of the package container 100, or a combination thereof.

The delivery management server 252 generates return information 225 inresponse to receiving the return request notification 223, the recipientreturn information, or both. In a particular aspect, the returninformation 225 includes instructions for returning the item 170,instructions for proper use of the item 170, assembly instructions forthe item 170, comments on the reason for returning the item 170, anoffer to extend a return window by a particular duration, an incentive(e.g., a partial refund, a discount on a future purchase, reward points,or a combination thereof) to keep the item 170, an incentive to returnthe item 170 sooner, or a combination thereof.

The delivery management server 252, the package container 100, and theuser device 250 enable implementation of various tiers of returnpolicies and incentives to customers (e.g., buyers, recipients, or acombination thereof) that can be dynamically adjusted over time basedupon various factors and conditions. In a particular example, the offerto extend the return window indicates a longer duration for recipientsthat are members of a loyalty program. As another example, the offeredincentives to keep the item 170 are based on a condition of the item 170detected based on sensor information received from the package container100.

In a particular example, the recipient may want to return the item 170because of a common user mistake in using the item 170 and the returninformation 225 indicates the proper use of the item 170. In aparticular example, a customer service agent may review the reason forreturning the item 170, provide comments addressing the reason, and thereturn information 225 includes the comments. The delivery managementserver 252 sends the return information 225 to the user device 250, thepackage container 100, or both. In a particular aspect, the packagecontainer 100 thus initiates sending of the return information 225 tothe user device 250 by sending the return request notification 223 tothe delivery management server 252.

The user device 250 displays the return information 225. The recipientmay follow the instructions to return the item 170. In a particularexample, the instructions to return the item 170 indicate that the item170 is to be placed in the package container 100, the cover 110 is to beclosed, and the package container 100 is to be placed at a particularlocation (e.g., an anchor point) for pick up. The recipient places theitem 170 in the package container 100. In a particular aspect, therecipient sends a close lid command 227 via the user device 250 to thepackage container 100. The container manager 132, in response toreceiving the close lid command 227 and determining that cover 110 is inan open state, sends a command to move the cover 110 from the open stateto a closed state. In an alternative aspect, the recipient physicallycloses the cover 110 (e.g., instead of sending the close lid command 227to the package container 100). The container manager 132, in response todetermining that the cover 110 is in the closed state subsequent toreceiving the return request 222, sends a closed notification 229 to thedelivery management server 252.

In a particular aspect, the recipient has a first time period (e.g., 15minutes) subsequent to sending the return request 222 to change theirmind about returning the item 170. For example, the recipient may changetheir mind based on receiving the return information 225. To illustrate,the recipient may, via the user interface 112 or the user device 250,accept the offer of an extended return window or accept the incentive tokeep the item 170. Accepting the offer of the extended return windowincreases the return window by a particular duration and cancels therequested return. In a particular aspect, accepting the incentive tokeep the item 170 corresponds to expiration (e.g., a reduction) of thereturn window and cancelation of the requested return. In a particularaspect, the recipient can cancel the requested return via the userinterface 112. For example, the recipient can press the button again tocancel the requested return. In a particular example, the button emits afirst light (e.g., a red light) to indicate that a return is requestedand a second light (e.g., a green light) to indicate that a return iscanceled/not requested. In a particular aspect, the container manager132 can automatically cancel the requested return based at least in parton detecting that the cover 110 is in an open state at the end of thefirst time period. For example, the container manager 132, in responseto detecting that the cover 110 is in an open state during (e.g., thelast 5 minutes of) the first time period, initiate display of an alertindicating that the user should place the item 170 in the packagecontainer 100 and close the cover 110 by the end of the first timeperiod to continue with the return. The container manager 132 cancelsthe return in response to determining that the cover 110 is in the openstate at the end of the first time period. The container manager 132, inresponse to determining that return has not been canceled within thefirst time period and that the cover 110 is in the closed state, sendsthe closed notification 229 to the delivery management server 252. In aparticular aspect, the container manager 132 stores a closed time in thememory 134. The closed time is based on a time at which the cover 110 isdetected as moving from the opened state to the closed state, a time atwhich the cover 110 is detected to be in the closed state, a time atwhich the closed notification 229 is sent to the delivery managementserver 252, or a combination thereof.

In a particular aspect, the delivery management server 252, in responseto receiving the closed notification 229, checks whether the trial hasended within the return window. For example, the delivery managementserver 252 stores a server trial end time that is based on a time atwhich the closed notification 229 is received by the delivery managementserver 252. The delivery management server 252 determines a server trialduration based on a comparison of the server trial start time and theserver trial end time. The delivery management server 252 determinesthat the trial has ended within the return window in response todetermining that the server trial duration satisfies (e.g., is less thanor equal to) a trial duration threshold (e.g., return window+tolerancethreshold). In a particular example, the recipient closes the cover 110at a first time, the recipient sends the return request 222 at a secondtime, a time period to cancel the return expires at a third time, thecontainer manager 132 sends the closed notification 229 at a fourthtime, and the delivery management server 252 receives the closednotification 229 at a fifth time. In a particular aspect, the tolerancethreshold accounts for an expected delay between the second time (whenthe cover 110 is closed and the return request 222 is sent) and thefifth time (when the delivery management server 252 receives the closednotification 229).

The delivery management server 252, in response to determining that thetrial has not ended within the return window, sends an invalid returnalert to the package container 100, the user device 250, or both. Thepackage container 100, the user device 250, or both, display the invalidreturn alert. In a particular example, the invalid return alertindicates that the trial period has expired, that automatic return ofthe ordered item (e.g., the item 170) is no longer available, that therecipient can contact customer service for further assistance, or acombination thereof.

The delivery management server 252, in response to receiving the closednotification 229, determining that the trial has ended within the returnwindow, or both, initiates retrieval of the package container 100, sendsthe lock command 207 to the package container 100, sends a trial endnotification 233 to the user device 250, or a combination thereof. Forexample, the delivery management server 252, in response to receivingthe closed notification 229, sends a delivery request to a deliverytruck to retrieve the package container 100 from the deliverydestination (e.g., the previous delivery destination). In a particularaspect, the delivery request indicates a next delivery destination ofthe package container 100. For example, the next delivery destinationindicates a warehouse or a second delivery destination (e.g., associatedwith a second order). In a particular example, the delivery managementserver 252, in response to receiving the closed notification 229,generates the trial end notification 233 indicating that the trial ofthe ordered item (e.g., the item 170) has ended. For example, the trialend notification 233 indicates that the trial of the ordered item (e.g.,the item 170) has ended. In a particular aspect, the trial endnotification 233 indicates information regarding pickup of the packagecontainer 100. For example, the trial end notification 233 indicatesthat retrieval of the package container 100 has been initiated, that thepackage container 100 has to be available for retrieval at a particularlocation by a particular time, that a refund for the ordered item (e.g.,the item 170) is being processed, that a refund for the ordered item(e.g., the item 170) will be processed subsequent to retrieval of thepackage container 100, or a combination thereof. The user device 250displays the trial end notification 233. The container manager 132, inresponse to receiving the lock command 207 and detecting that the cover110 is in an opened state, displays an alert, initiates cancelation ofthe return request, or both. Alternatively, the container manager 132activates the cover lock 115 in response to receiving the lock command207 and detecting that the cover 110 is in a closed state. In aparticular aspect, the package container 100 is considered to be at thedelivery location between sending the delivery notification 209 andreceiving the lock command 207.

In a particular aspect, the recipient places the package container 100at a pickup location (e.g., at an anchor point or outside a front door)after receiving the trial end notification 233 and the package container100 is retrieved by the delivery truck. It should be understood that adelivery truck retrieving the package container 100 is used as anillustrative example. The package container 100 can be transported usingone or more modes of transportation, such as a human carrier, a robot, abicycle, an aircraft, a truck, a van, an unmanned aerial vehicle, aself-driving vehicle, a watercraft, or a combination thereof. In aparticular aspect, the container manager 132 detects a location of thepackage container 100 (e.g., a container location) in response toreceiving location information (e.g., global positioning system (GPS)information or an anchor point identifier) indicating that the packagecontainer 100 has arrived at the location, receiving a user input viathe user interface 112 (or a transceiver) indicating that the packagecontainer 100 has arrived at the location, or both. In a particularaspect, the location information is based on a location of a GPSreceiver of the package container 100, a location of a GPS receiver of atransportation vehicle, a location of a location beacon, or acombination thereof. The container manager 132, in response todetermining that the container location includes a location of an anchorpoint, a location of a transportation vehicle, a location of awarehouse, a location of an airport, a location of a transportation hub,or a combination thereof, detects arrival of the package container 100at a merchant location. The container manager 132, in response todetecting arrival at the merchant location, sends a return notification235 to the delivery management server 252.

In a particular aspect, the container manager 132 sends package data tothe delivery management server 252 in response to detecting arrival atthe merchant location. In an alternative aspect, the delivery managementserver 252 retrieves the package data from the package container 100 inresponse to receiving the return notification 235. The package dataincludes the trail start time (e.g., a package trial start time), thetrial end time (e.g., a package trial end time), or both. In aparticular aspect, the delivery management server 252 sends an alert toa device of a customer services representative in response todetermining that a difference between the server trial start time andthe package trial start time exceeds a trial start time threshold, thata difference between the server trial end time and the package trial endtime exceeds a trial end time threshold, or both. In a particularaspect, the delivery management server 252 updates the server trialstart time and the server trial end time based on the package trialstart time and the package trial end time, respectively.

In a particular aspect, the delivery management server 252 determines areturn time based on a time at which the return notification 235 isreceived. In a particular aspect, the delivery management server 252determines a return duration based on a comparison of the server trialend time and the return time. In a particular aspect, the deliverymanagement server 252 sends an alert to a device of a customer servicesrepresentative in response to determining that a difference between theserver trial end time and the return duration exceeds a return timethreshold.

In a particular aspect, the delivery management server 252 determines arefund amount based on the server trial duration, the return duration,or both. For example, a shorter return duration corresponds to a higherrefund amount to incentivize the recipient to make the package container100 available for pickup soon after receiving the trial end notification233. In a particular aspect, the delivery management server 252determines the refund amount based at least in part on the item 170. Forexample, a customer service agent retrieves the item 170 from thepackage container 100 and provides item condition information to thedelivery management server 252. In another example, the deliverymanagement server 252 receives the item condition information based oninput received from one or more sensors (e.g., a camera), the packagecontainer 100, or a combination thereof. The delivery management server252 adjusts the refund amount based at least in part on the itemcondition information. In a particular example, the delivery managementserver 252 reduces the refund amount in response to determining that theitem condition information indicates that the item 170 is badly damaged.In another example, the delivery management server 252 increases therefund amount in response to determining that the item conditioninformation indicates that the item 170 is badly damaged and determiningthat the data retrieved from the package container 100 indicate that thepackage container 100 experienced transport conditions (e.g., strong andabrupt movement, a higher than threshold temperature, a lower thanthreshold temperature, etc.) that could have caused the damage to theitem 170 during transportation to or from the delivery location. In aparticular aspect, the delivery management server 252 sends refundinformation (e.g., the refund amount and explanation regardingcalculation of the refund amount) to the user device 250, updates anaccount of the buyer based on the refund information, updates an accountof the recipient based on the refund information, or a combinationthereof.

In an example 300 illustrated in FIG. 3, the package container 100 hasenhanced capabilities and has less reliance on remote communicationswith the delivery management server 252. During the order stage 206 ofthe example 300, the delivery management server 252, in response toreceiving the order information 201, sends the order information 201,authentication information 301, or both, to the package container 100.The package container 100 stores the order information 201, theauthentication information 301, or both, in the memory 134. In aparticular aspect, the delivery management server 252 provides theauthentication information 301 to the package container 100 to enablethe package container 100 to perform local authentication (as comparedto relying on the delivery management server 252 to perform remoteauthentication, as described in reference to the example 200) of arecipient of the package container 100, as described herein.

The container manager 132 activates the cover lock 115, at 303, inresponse to detecting that the cover 110 is in the closed state,receiving user input indicating that the cover 110 is to be locked, orboth (as compared to in response to receiving the lock command 207 fromthe delivery management server 252), as described with reference to theexample 200). The container manager 132 sends a lock notification 305 tothe delivery management server 252 in response to activating the coverlock 115. In a particular aspect, the delivery management server 252, inresponse to receiving the lock notification 305, updates an order statusindicating that at least one item of the order is ready for shipping.The package container 100 is considered to be located at a merchantlocation (e.g., a warehouse of a seller, a warehouse of a retailer, awarehouse of a delivery company, a store, a delivery truck, an anchorpoint, or a combination thereof) prior to sending the lock notification305.

During the shipment stage 208 of the example 300, the container manager132, in response to detecting arrival at the delivery location, sendsthe delivery notification 209 to the user device 250, the deliverymanagement server 252, or both (as compared to the delivery managementserver 252 forwarding the delivery notification 209 from the packagecontainer 100 to the user device 250, as described with reference to theexample 200). The package container 100 is considered to be in transitbetween sending the lock notification 305 and sending the deliverynotification 209.

During the trial stage 210 of the example 300, the user device 250 sendsthe unlock request 213 to the package container 100 to trigger localauthentication 311 (as compared to sending the unlock request 213 to thedelivery management server 252 to trigger remote authentication at thedelivery management server 252, as described with reference to theexample 200). For example, the container manager 132 performs localauthentication 311 by comparing user credentials indicated in the unlockrequest 213 with the authentication information 301. To illustrate, thecontainer manager 132 determines that authentication is successful inresponse to determining that the user credentials match theauthentication information 301. The container manager 132 deactivatesthe cover lock 115, at 313, in response to determining that theauthentication is successful. The container manager 132 sends the trialstart notification 221 to the user device 250 (as compared to sendingthe opened notification 219 to the delivery management server 252 totrigger sending of the trial start notification 221 from the deliverymanagement server 252 to the user device 250, as described withreference to the example 200) in response to detecting, for the firsttime subsequent to deactivating the cover lock 115, that the cover 110is in the opened state at an opened time. The container manager 132determines a trial start time 319 based on the opened time, a time atwhich the trial start notification 221 is sent to the user device 250,or both. The container manager 132 sends the trial start time 319 to thedelivery management server 252. The delivery management server 252starts a trial timer, at 321. For example, the delivery managementserver 252 stores the trial start time 319 as a server trial start time.

During the return stage 212 of the example 300, the container manager132, in response to receiving the return request 222, sends the returninformation 225 to the user device 250 (as compared to sending thereturn request notification 223 to the delivery management server 252 totrigger sending of the return information 225 from the deliverymanagement server 252 to the user device 250, as described withreference to the example 200). The container manager 132 activates thecover lock 115, at 325, in response to determining that the cover 110 isin the closed state subsequent to receiving the return request 222 (ascompared to in response to receiving the lock command 207 from thedelivery management server 252, as described with reference to theexample 200 of FIG. 2). The container manager 132, subsequent toactivating the cover lock 115, sends the trial end notification 233 tothe user device 250 (as compared to sending the closed notification 229to the delivery management server 252 to trigger the delivery managementserver 252 to send the trial end notification 233 to the user device250, as described with reference to the example 200). The containermanager 132 requests transport, at 329, subsequent to sending the trialend notification 233 to the user device 250. For example, the containermanager 132 sends a delivery request to a delivery truck to retrieve thepackage container 100 from the delivery destination.

The container manager 132 determines a trial end time 331 based on aclosed time at which the cover 110 is detected as closed subsequent toreceiving the return request 222, a lock time at which the cover lock115 is activated, a trial end notification time at which the trial endnotification is sent to the user device 250, a request transport time atwhich the delivery request is sent, or a combination thereof. Thecontainer manager 132 sends the trial end time 331 to the deliverymanagement server 252. In a particular aspect, the package container 100is considered to be at the delivery location between sending thedelivery notification 209 and sending the trial end time 331. Thedelivery management server 252 stores the trial end time 331 as theserver trial end time. The delivery management server 252 determines aserver trial duration based on a comparison of the server trial starttime and the server trial end time, at 333. In a particular aspect, thepackage container 100 is considered to be in transit between sending thetrial end time 331 and sending the return notification 235.

In example 400 of FIG. 4, the package container 100 has limitedcapabilities and relies on the user device 250 for remote communicationwith the delivery management server 252. During the shipment stage 208of the example 400, the delivery management server 252 receives adelivery notification 409 from a delivery system (e.g., a deliveryvehicle) indicating that the package container 100 has arrived at thedelivery location. The delivery management server 252 forwards thedelivery notification 409 received from the delivery system to the userdevice 250 (e.g., a user device associated with the intended recipient,a user device associated with the buyer, or both). In a particularaspect, the container manager 132, in response to detecting arrival atthe delivery location, sends the delivery notification 209 to the userdevice 250 (as compared to sending the delivery notification 209 to thedelivery management server 252, as described with reference to theexample 200). The user device 250 receives the delivery notification 409(generated by the delivery system) from the delivery management server252, the delivery notification 209 (generated by the container manager132) from the package container 100, or both. In a particular aspect,the package container 100 is considered to be in transit betweenreceiving the lock command 207 and sending the delivery notification209. In a particular aspect, the package container 100 is considered tobe in transit between receiving the lock command 207 and the deliverymanagement server 252 receiving the delivery notification 409.

During the trial stage 210 of the example 400, the user device 250 sendsthe unlock request 213 to the delivery management server 252 (ascompared to sending the unlock request 213 to the package container 100,as described with reference to the example 200). The delivery managementserver 252 performs remote authentication 403, in response to receivingthe unlock request 213 from the user device 250. For example, the unlockrequest 213 indicates user credentials and the delivery managementserver 252 authenticates the unlock request 213 based on a comparison ofthe user credentials and the authentication information 301. Thedelivery management server 252, in response to determining that the usercredentials match the authentication information 301, sends an unlockcode 405 to the user device 250. The user device 250 forwards the unlockcode 405 received from the delivery management server 252 to the packagecontainer 100. The container manager 132 deactivates the cover lock 115,at 313, in response to determining that the unlock code 405 matches avalid unlock code of the package container 100. In a particular aspect,the unlock code 405 received from the delivery management server 252 isdigitally signed using an encryption key of the package container 100,an encryption key of the delivery management server 252, or both. Forexample, the unlock code 405 received from the delivery managementserver 252 is digitally signed using a private encryption key of thedelivery management server 252 and the container manager 132 extractsthe unlock code 405 using a public encryption key of the deliverymanagement server 252. In the example 400, the delivery managementserver 252 performs the remote authentication 403 as compared to thepackage container 100 performing local authentication 311 (as describedwith reference to the example 300).

The container manager 132, in response to detecting that the cover 110is an opened state subsequent to deactivating the cover lock 115, sendsthe trial start time 319 to the user device 250 (as compared to sendingthe trial start time 319 to the delivery management server 252, asdescribed with reference to the example 300 of FIG. 3). The user device250 forwards the trial start time 319 received from the packagecontainer 100 to the delivery management server 252. In a particularaspect, the trial start time 319 received from the package container 100is digitally signed using an encryption key of the package container100, an encryption key of the user device 250, an encryption key of thedelivery management server 252, or a combination thereof.

The delivery management server 252 sends the trial start notification221 to the user device 250 in response to receiving the trial start time319 from the user device 250 (as compared to receiving the openednotification 219 from the package container 100, as described withreference to the example 200). In a particular aspect, the deliverymanagement server 252 generates a reminder 407 and sends the reminder407 to the user device 250. For example, the delivery management server252 determines a reminder time based on the trial start time 319 (e.g.,10:00 AM) and a trial duration threshold (e.g., reminder time=trialstart time+0.75 (trial duration threshold)). The delivery managementserver 252 generates the reminder 407 indicating an available time(e.g., available time=0.25 (trial duration threshold)) to initiate areturn of the item 170. The delivery management server 252 initiatesdisplay of the reminder 407 based on the reminder time. For example, thedelivery management server 252 sends the reminder 407 to the user device250 at approximately the reminder time, sends a request to the userdevice 250 to display the reminder 407 at the reminder time, or both.The user device 250 displays the reminder 407.

During the return stage 212 of the example 400, the container manager132, responsive to receiving the return request 222 from the userinterface 112, sends the return request notification 223 to the userdevice 250 (as compared to sending the return request notification 223to the delivery management server 252, as described with the example200). In a particular aspect, the user interface 112 sends the returnrequest 222 to the container manager 132 in response to detecting that auser has activated the user interface 112 (e.g., pressed a button). Theuser device 250 forwards the return request notification 223 receivedfrom the package container 100 to the delivery management server 252. Ina particular aspect, the return request notification 223 is sent to theuser device 250 of a buyer, the user device 250 of an intendedrecipient, or both. In a particular aspect, the user device 250 displaysthe return request notification 223 and selectively forwards the returnrequest notification 223 to the delivery management server 252responsive to a user input confirming the return request. The userconfirmation prevents a return request initiated by an unauthorized user(e.g., other than the buyer or intended recipient, such as a childplaying with the package container 100) to be sent to the deliverymanagement server 252.

In a particular aspect, the return information 225 requests informationregarding the item being returned. The user device 250 provides returnitem information 411 to the package container 100. For example, thereturn item information 411 includes an ordered item identifier of theordered item, an item identifier of the item 170, a reason for returningthe item 170, or a combination thereof.

In a particular aspect, the container manager 132, subsequent toactivating the cover lock 115, sends the trial end time 331 to the userdevice 250 (as compared to sending the trial end time 331 to thedelivery management server 252, as described with reference to theexample 300). The user device 250 forwards the trial end time 331received from the package container 100 to the delivery managementserver 252.

The container manager 132, in response to detecting arrival of thepackage container 100 at the merchant location, sends data 413 to thedelivery management server 252. For example, the container manager 132sends the data 413 concurrently with sending the return notification 235to the delivery management server 252. In a particular aspect, the data413 includes the return item information 411, sensor input from one ormore sensors, a trial start time, a trial end time, a timestampedlisting of communications sent or received, or a combination thereof. Ina particular aspect, the delivery management server 252 adjusts a refundamount based at least in part on the data 413. For example, the deliverymanagement server 252 reduces the refund amount in response todetermining that data 413 indicates that the item 170 is badly damaged.In another example, the delivery management server 252 increases therefund amount in response to determining that the data 413 includes aphotograph indicating that the item 170 is badly damaged and that thedata 413 includes sensor data indicating the package container 100experienced transport conditions (e.g., strong and abrupt movement, ahigher than threshold temperature, a lower than threshold temperature,etc.) that could have caused the damage to the item 170 duringtransportation to the delivery location. In a particular aspect, thedelivery management server 252 sends account information 415 (e.g., therefund amount and explanation regarding calculation of the refundamount) to the user device 250, updates an account of the buyer based onthe account information 415, updates an account of the recipient basedon the account information 415, or a combination thereof.

The package container 100 can thus be used for all three examples(200-400) depending on security requirements, supported capabilities, ora combination thereof. One or more operations of the examples 200-400can be mixed and matched. For example, the delivery management server252 can send the unlock code 405 to the user device 250 (as compared tosending the unlock command 215 to the package container 100) in theexample 200. The package container 100 enables a trial to start afterthe package container 100 is opened. Since the trial starts after thepackage container 100 is opened, a shorter trial period (e.g., 2 hours)gives a recipient time to try out the item 170 regardless of whether thepackage container 100 is opened soon after delivery or days afterdelivery. The shorter trial period (e.g., 2 hours) reduces a likelihoodof the recipient using the item 170 (e.g., wearing a jacket to a party)before returning the item 170. For a recipient who open the packagecontainer 100 soon after delivery and decides to return the item 170,the item 170 has to be returned within the shorter trial period (e.g., 2hours) for a refund (e.g., a full refund) and becomes available early(e.g., sooner than for a two week return window) for reselling to otherconsumers. In some examples, if the package container 100 is not openedwithin a threshold duration of delivery, a reminder can be displayed toencourage the recipient to open the package container 100, to inform therecipient regarding an available trial time remaining to receive arefund (e.g., a full refund available for another 6 hours, a half refundavailable after 6 hours, and non-refundable after 1 day), or both. Insome examples, if the package container 100 is not opened and remainsattached to an anchor point within a threshold duration of delivery, thecontainer manager 132 (or the delivery management server 252) requeststransport. For example, the container manager 132 (or the deliverymanagement server 252) sends a delivery request to a delivery truck toretrieve the package container 100 from the delivery destination.

The package container 100 can also enable convenient returns. Forexample, the recipient can activate a button (e.g., the user interface112) of the package container 100 to request a return, place the item170 in the package container 100, close the cover 110 of the packagecontainer 100, and place the package container 100 outside for pickup.The package container 100 activates the cover lock 115 of the packagecontainer 100 and sends a transportation request to initiatetransportation of the package container 100.

FIG. 5 is a diagram of one exemplary embodiment of the componentsincluded in the package container 100. In the embodiment illustrated,the package container 100 includes the cover lock 115, the first lockingbar 120, the second locking bar 125, the electronic controller 130, atransceiver 505, the user interface 112, a power supply module 515, anda plurality of sensors 520.

The electronic controller 130 includes, among other things, thecontainer manager 132 (e.g., an electronic processor, such as amicroprocessor), the memory 134, an input/output interface 535, and abus. The bus connects various components of the electronic controller130 including the memory 134 to the container manager 132. The memory134 includes read only memory (ROM), random access memory (RAM), anelectrically erasable programmable read-only memory (EEPROM), othernon-transitory computer-readable media, or any combination thereof. Thecontainer manager 132 is configured to retrieve program instructions anddata from the memory 134 and execute, among other things, instructionsto perform the methods described herein. Additionally or alternatively,the memory 134 is included in the container manager 132. Theinput/output interface 535 includes routines for transferringinformation between components within the electronic controller 130 andother components of internal and external to the package container 100.

The transceiver 505 is configured to provide communications between thepackage container 100 and the user device 250, the delivery managementserver 252, or a combination thereof. The transceiver 505 transmitssignals to one or more communication networks and receives signals fromthe communication networks. In some embodiments, signals include, forexample, data, data packets, or any combination thereof. In someembodiments, the transceiver 505 includes separate transmitters andreceivers. The communication network may be implemented using variousnetworks, for example, a cellular network, the Internet, a Bluetooth™network, a wireless local area network (for example, Wi-Fi), a wirelessaccessory Personal Area Networks (PAN), cable, an Ethernet network,satellite, a machine-to-machine (M2M) autonomous network, and a publicswitched telephone network.

The user interface 112 can include any combination of digital and analoginput or output devices required to achieve a desired level of controlfor the package container 100. For example, the user interface 112 caninclude a display, a camera, a speaker, a microphone, a fingerprintsensor, a plurality of knobs, dials, switches, buttons, and the like. Toillustrate, the speaker can be used to generate audible output (e.g.,speech, tone, or both). The microphone can be used to receive audibleinput (e.g., speech). In some embodiments, the user interface 112includes a touch-sensitive interface (for example, touch-screen display)that displays visual output generated by software applications executedby the container manager 132. Visual output includes, for example,graphical indicators, lights, colors, text, images, graphical userinterfaces (GUIs), combinations of the foregoing, and the like. Thetouch-sensitive interface includes a suitable display mechanism fordisplaying the visual output (for example, a light-emitting diode (LED)screen, a liquid crystal display (LCD) screen, and the like). Thetouch-sensitive interface also receives user input using detectedphysical contact (for example, detected capacitance or resistance).Based on the user input, the touch-sensitive interface outputs signalsto the container manager 132 which indicate positions on thetouch-sensitive interface currently being selected by physical contact.In some implementations, the user interface 112 includes a wirelessdevice, a mobile device, or both. In some implementations, the userinterface 112 is included in (e.g., physically attached to) the packagecontainer 100. In other implementations, the user interface 112 isremote from (e.g., not physically attached to) the package container100. In a particular aspect, the user interface 112 includes the userdevice 250. In a particular example, the user device 250 corresponds toan extension of the user interface 112. The user interface 112 iscoupled to the package container 100. As used herein, “coupled” mayinclude “communicatively coupled,” “electrically coupled,” or“physically coupled,” and may also (or alternatively) include anycombinations thereof. Two devices (or components) may be coupled (e.g.,communicatively coupled, electrically coupled, or physically coupled)directly or indirectly via one or more other devices, components, wires,buses, networks (e.g., a wired network, a wireless network, or acombination thereof), etc. Two devices (or components) that areelectrically coupled may be included in the same device or in differentdevices and may be connected via electronics, one or more connectors, orinductive coupling, as illustrative, non-limiting examples. As usedherein, “directly coupled” may include two devices that are coupled(e.g., communicatively coupled, electrically coupled, or physicallycoupled) without intervening components.

The power supply module 515 supplies a nominal AC or DC voltage to thepackage container 100. In some embodiments, the power supply module 515is powered by one or more batteries or battery packs including in thepackage container 100. The power supply module 515 is also configured tosupply lower voltages to operate circuits and components within thepackage container 100. In some embodiments, the power supply module 515is powered by household power having nominal line voltages between, forexample, 100 volts AC and 240 volts AC and frequencies of approximately50 hertz to 60 hertz. In some embodiments, the power supply module 515is powered by inductive charging, solar charging, or both.

The plurality of sensors 520 includes various sensors configured todetect various conditions of the package container 100. In someembodiments, the plurality of sensors 520 includes location sensors 540,environmental sensors 545, movement sensors 550, audio sensors 555,electrical sensors 560, or any combination thereof.

Location sensors 540 (for example, global positioning system (GPS)sensors) are used to determine an absolute or relative location of thepackage container 100. As explained above, in some examples, the packagecontainer 100 is secured to an anchoring point upon being delivered. Insome embodiments, the electronic controller 130 ensures that the packagecontainer 100 has been delivered to the correct anchoring point bycomparing the current location of the package container 100 (determinedusing the location sensors 540) to a location of a target anchor point.In some embodiments, the location sensors 540 determine the location ofthe package container 100 periodically. Alternatively and in addition,the location sensors 540 determine the location of the package container100 in response to receiving a request (for example, via the transceiver505). For example, the recipient or sender of the package container 100sends a request signal to the electronic controller 130, via thetransceiver 505, requesting a location of the package container 100. Inresponse, the electronic controller 130 determines a current (or lastknown) location of the package container 100, via the location sensors540, and transmits the location to the recipient or sender, via thetransceiver 505. In some embodiments, the electronic controller 130determines the location of the package container 100 based at least inpart on one or more location signals received via the transceiver 505.

Environmental sensors 545 (for example, temperature sensors, humiditysensors, chemical sensors, and biological sensors) are used to determinethe environmental conditions of the package container 100. For example,the environmental sensors 545 may be placed within the cavity 165 of thepackage container 100 and configured to determine the temperature andhumidity. In some embodiments, the electronic controller 130 determineswhether predetermined environmental conditions exist within the packagecontainer. For example, when the package container 100 is transported anitem that requires a temperature below a set threshold, the electroniccontroller 130 continuously determines the temperature within thepackage container 100, via the environmental sensors 545, and transmitsan alert signal when the temperature rises above the set threshold. Insome examples, the environmental sensors 545 detect conditions externalto the package container 100. For example, the electronic controller 130tracks temperatures external to the package container 100, via theenvironmental sensors 545, and transmits the external temperatures. Theexternal temperatures can indicate thermal challenges in maintaining atemperature within the package container 100 within the set thresholddue to external conditions (e.g., too high external temperature or toolow external temperature).

Movement sensors 550 (for example, an accelerometer, gyroscope, or amagnetometer) are used to detect movement of the package container 100.The ability to detect movement of the package container 100 provides aplurality of benefits. For example, while a normal level of movement isto be expected while the package container 100 is being transported, anexcessive amount of movement (for example, movement caused by thepackage container 100 being dropped) may indicate mishandling. In someembodiments, the electronic controller 130 uses the movement sensors 550to detect when the amount of movement is above a set threshold andtransmits an alert signal to, for example, the sender, the buyer, theintended recipient, the shipping company, or any combination thereof.These alerts signal may be used to determine the cause of damagedpackages.

Another benefit of movement sensors 550 is added security. For example,after being secured to an anchoring point the package container 100should not be moving until the recipient retrieves the packages.Movement of the package container 100 after being secured to an anchorpoint and prior to being retrieved by the recipient could indicate apotential theft attempt. Thus, in some embodiments, the electroniccontroller 130 detects such improper movement of the package container100 and transmits an alert signal to, for example, the sender, thebuyer, the intended recipient, the shipping company, or any combinationthereof.

Audio sensors 555 (for example, a microphone) are used to record noisepresent around the package container 100. For example, the audio sensors555 can record audio during a potential theft of the package container100 while it is secured to an anchor point. The recorded audio can laterbe used to determine the identity of the party attempting to steal thepackage container 100. In a particular aspect, the user interface 112includes one or more of the audio sensors 555.

The electrical sensors 560 are used to detect movement of the cover 110between an opened state and a closed state. For example, the containermanager 132 can determine that a trial has started in response todetecting, based on input from the electrical sensors 560, that thecover 110 has moved from the closed state to the opened state for thefirst time subsequent to arrival at a delivery location. Electricalsensors 560 are provided as an illustrative example of sensors that canbe used to detect movement of the cover 110. In other implementations,various types of sensors can be used to detect movement of the cover110, such as a magnetic sensor (e.g., a hall effect sensor, a reed relaysensor, or both), an electrical contact sensor, a camera, or anothertype of sensor.

FIG. 6 illustrates an exemplary method 600 of returning the packagecontainer 100. In the example illustrated, the method 600 includes thememory 134 of the package container 100 storing the order information201 (at block 605). At block 610, the container manager 132 detects, ata first time, that the cover 110 of the package container 100 has movedfrom a closed state to an open state. For example, the cover 110 isadjusted from the closed position to the open position for a recipientto retrieve the item 170 from the cavity 165 of the package container100.

At block 615, the container manager 132 stores a trial start time in thememory 134 of the package container 100. The trial start time is basedon the first time. In a particular example, a trial of the item 170starts at the trial start time.

At block 620, the container manager 132 determines a reminder time(e.g., 11:30 AM) based on the trial start time (e.g., 10:00 AM) and atrial duration threshold (e.g., reminder time=trial starttime+0.75*trial duration threshold). For example, the trial durationthreshold indicates a return window (e.g., 2 hours) during which areturn can be initiated for a refund. The reminder time is subsequent tothe trial start time and prior to expiration of the return window.

At block 625, the container manager 132 initiates display of a reminderbased on the reminder time. For example, the container manager 132 sendsa reminder to the user device 250 at the reminder time for display,sends a request to the user device 250 to display the reminder at thereminder time, provides the reminder at the reminder time to the userinterface 112 for display, or a combination thereof.

At block 630, the container manager 132 receives the return request 222via the user interface 112. For example, a recipient activates the userinterface 112 (e.g., a button) to request a return of the item 170. Atblock 635, the container manager 132, based at least in part on thereturn request 222 and detecting that the cover 110 is in a closedstate, stores a second time as a trial end time in the memory 134.

The package container 100 includes a unique identifier (for example, aunique code) that is used to distinguish the package container 100 froma different package container. In some embodiments, the uniqueidentifier for the package container 100 is electronically readable. Forexample, the unique identifier is stored in the memory 134 of theelectronic controller 130. As a further example, the unique identifieris stored in an electronically readable tag included in the packagecontainer 100 such as a radio frequency identification (RFID) tag or anear-field communication (NFC) tag. Alternatively or in addition, theunique identifier is optically readable on the package container 100.For example, the unique identifier is a barcode (or QR code) imageattached to an outer surface of the body 105 or displayed by atouch-screen display included in the user interface 112.

The unique identifier eliminates the need to place a new physical labelon the package container 100 for each subsequent delivery of the packagecontainer 100. Rather, the input for each delivery (for example,destination information, pick-up information, etc.) is associated withthe unique identifier of the package container 100.

In a particular aspect, a package container includes a body, a cover, acover lock, a user interface, and an electronic controller. The body hasa base, an opening, and at least one side wall that define a cavitytherebetween. The cover is coupled to the body. The cover is movablefrom a closed state covering the opening to an open state. The coverlock is configured to, when activated, keep the cover in the closedstate. The electronic controller is coupled to the user interface andthe cover lock. The electronic controller includes a memory and aprocessor. The processor is configured to store order information in thememory. The order information indicates that the package container isassigned to transport one or more items in the cavity. The processor isalso configured to detect, at a first time, that the cover has movedfrom the closed state to the open state. The processor is furtherconfigured to store a trial start time that is based on the first time.The processor is also configured to receive a return request via theuser interface. The processor is further configured to, based at leastin part on receiving the return request and detecting that the cover isin the closed state, store a second time as a trial end time, and send atransportation request to a delivery management server to initiatetransportation of the package container.

In another particular aspect, a method includes storing, in a memory ofa package container, order information indicating that the packagecontainer is assigned to transport one or more items. The method alsoincludes detecting, at a first time at an electronic controller of thepackage container, that a cover of the package container has moved froma closed state to an open state. The method further includes storing atrial start time that is based on the first time. The method alsoincludes determining a reminder time based on the trial start time and atrial duration threshold. The method further includes initiating displayof a reminder based on the reminder time. The reminder indicatesavailable time to initiate return of the one or more items. The methodalso includes receiving, at the electronic controller, a return requestvia a user interface. The method further includes, based at least inpart on receiving the return request and detecting that the cover is inthe closed state, storing a second time as a trial end time.

In another particular aspect, a method includes receiving, at a userdevice, a trial start notification from at least one of a packagecontainer or a delivery management server. The trial start notificationindicates initiation of a trial of one or more items. The one or moreitems are assigned for transportation to the package container. Themethod also includes providing the trial start notification to adisplay. The method further includes receiving, at the user device, areturn request notification from the package container. The method alsoincludes, in response to receiving the return request notification fromthe package container, sending the return request notification from theuser device to a delivery management server. The method further includesreceiving, at the user device from the delivery management server,return information responsive to the return request notification. Themethod also includes providing the return information to the display.The method further includes receiving, at the user device, a trial endtime of the trial from the package container. The method also includessending the trial end time to the delivery management server to initiatetransportation of the package container. The method further includesreceiving, at the user device, a trial end notification from at leastone of the package container or the delivery management server. Thetrial end notification indicates that the trial has ended. The methodalso includes providing the trial end notification to the display.

In another particular aspect, a method includes receiving, at a deliverymanagement server from at least one of a user device or a packagecontainer, an opened notification indicating that a cover of the packagecontainer has moved from a closed state to an open state. One or moreitems are assigned for transportation to the package container. Themethod also includes storing a trial start time in response to receivingthe opened notification. The method further includes receiving a returnrequest notification at the delivery management server from at least oneof the user device or the package container. The method also includes,subsequent to receiving the return request notification, receiving aclosed notification at the delivery management server from at least oneof the user device or the package container. The method furtherincludes, based on receiving the return request notification and theclosed notification, storing a trial end time and initiatingtransportation of the package container.

This disclosure is not limited in its application to the examplesprovided, the embodiments discussed, or to the details of constructionand the arrangement of components set forth in the foregoing descriptionor drawings. The disclosure is capable of other embodiments and of beingpracticed or of being carried out in various ways.

What is claimed is:
 1. A package container comprising: a body, the bodyhaving a base, an opening, and at least one side wall, wherein the base,the opening, and the at least one side wall define a cavitytherebetween; a cover coupled to the body, the cover movable from aclosed state covering the opening to an open state; a cover lockconfigured to, when activated, keep the cover in the closed state; auser interface; and an electronic controller coupled to the userinterface and the cover lock, the electronic controller including amemory and a processor, wherein the processor is configured to: storeorder information in the memory, the order information indicating thatthe package container is assigned to transport one or more items in thecavity to a delivery location; detect, at a first time, that the coverhas moved from the closed state to the open state; store a trial starttime that is based on the first time; receive a return request via theuser interface; and based at least in part on receiving the returnrequest and detecting that the cover is in the closed state: store asecond time as a trial end time; determine a trial duration based on acomparison of the trial start time and the trial end time; and initiatesending of a transportation request to a delivery management server inresponse to the processor determining that the trial duration is lessthan or equal to a trial duration threshold, the transportation requestindicating a request to initiate sending of a transportation vehicle tothe delivery location to retrieve the package container from thedelivery location.
 2. The package container of claim 1, wherein thereturn request indicates that a second item is to be returned in thepackage container, wherein the second item is distinct from the one ormore items, and wherein the trial end time is associated with the seconditem.
 3. The package container of claim 1, wherein the processor isfurther configured to activate the cover lock in response to receiving alock command from the delivery management server.
 4. The packagecontainer of claim 1, wherein the processor is further configured to, inresponse to receiving the return request, send a return requestnotification to the delivery management server, the return requestnotification corresponding to a request to initiate sending of returninformation to at least one of a user device or the user interface. 5.The package container of claim 1, wherein the processor is furtherconfigured to, subsequent to receiving the return request: based ondetecting that the cover is in the closed state, send a closednotification to the delivery management server, the closed notificationcorresponding to a request to initiate sending of a trial endnotification to a user device; receive a lock command from the deliverymanagement server responsive to the closed notification; and activatethe cover lock in response to receiving the lock command.
 6. The packagecontainer of claim 1, wherein the trial duration threshold is based on areturn window and a tolerance threshold.
 7. The package container ofclaim 1, wherein the processor is further configured to, in response toreceiving the return request, send return information via a transceiverto a user device.
 8. The package container of claim 1, wherein theprocessor is further configured to, subsequent to receiving the returnrequest and detecting that the cover is in the closed state: send atrial end notification via a transceiver to a user device; activate thecover lock; determine the second time based on at least one of a requesttime at which the return request is received, a closed time at which thecover is detected in the closed state, or a lock time at which the coverlock is activated; and send the trial start time, the trial end time, orboth, via the transceiver, to the delivery management server.
 9. Thepackage container of claim 1, wherein the processor is furtherconfigured to, in response to receiving the return request: send areturn request notification to a user device, the return requestnotification corresponds to a request to initiate sending of the returnrequest notification to the delivery management server; receive returnitem information from the user device; and store the return iteminformation in the memory.
 10. The package container of claim 1, whereinthe user interface is located at an exterior surface of at least one ofthe cover or the body.
 11. A method comprising: storing, in a memory ofa package container, order information indicating that the packagecontainer is assigned to transport one or more items to a deliverylocation; detecting, at a first time at an electronic controller of thepackage container, that a cover of the package container has moved froma closed state to an open state; storing, by the electronic controller,a trial start time that is based on the first time; determining, by theelectronic controller, a reminder time based on the trial start time anda trial duration threshold; initiating, by the electronic controller,display of a reminder based on the reminder time, the reminderindicating available time to initiate return of the one or more items;receiving, at the electronic controller, a return request via a userinterface of the package container; and based at least in part onreceiving the return request and detecting that the cover is in theclosed state: activating, by the electronic controller, a cover lock ofthe package container to keep the cover in the closed state; storing, bythe electronic controller, a second time as a trial end time;determining, by the electronic controller, a trial duration based on acomparison of the trial start time and the trial end time; andinitiating, by the electronic controller, sending of a transportationrequest to a delivery management server in response to determining, bythe electronic controller, that the trial duration is less than or equalto the trial duration threshold, the transportation request indicating arequest to initiate sending of a transportation vehicle to the deliverylocation to retrieve the package container from the delivery location.12. The method of claim 11, further comprising, subsequent to receivingthe return request and detecting that the cover is in the closed state,sending the trial end time to a user device, the sending of the trialend time corresponding to a request to initiate sending of the trial endtime to the delivery management server, wherein the second time is basedon a lock time at which the cover lock is activated by the electroniccontroller.
 13. The method of claim 12, further comprising: detecting acontainer location of the package container; and in response todetermining that the container location includes at least one of alocation of an anchor point, the transportation vehicle, or a warehouse,sending a return notification to the delivery management server.
 14. Themethod of claim 12, further comprising: detecting a container locationof the package container; and in response to determining that thecontainer location includes at least one of a location of an anchorpoint, the transportation vehicle, or a warehouse, sending the trial endtime to the delivery management server.
 15. A method comprising:storing, in a memory of a package container, order informationindicating that the package container is assigned to transport one ormore items to a delivery location; detecting, at a first time at anelectronic controller of the package container, that a cover of thepackage container has moved from a closed state to an open state;storing, by the electronic controller, a trial start time that is basedon the first time; receiving, at the package container, a return requestvia a user interface of the package container; and based at least inpart on receiving the return request and detecting at a second time thatthe cover has moved to the closed state: activating, by the electroniccontroller, a cover lock of the package container to keep the cover inthe closed state; storing, by the electronic controller, a third time asa trial end time, wherein the third time is the same as or after thesecond time; determining, by the electronic controller, a trial durationbased on a comparison of the trial start time and the trial end time;and initiating, by the electronic controller, sending of atransportation request to a delivery management server in response todetermining, by the electronic controller, that the trial duration isless than or equal to a trial duration threshold, the transportationrequest indicating a request to initiate sending of a transportationvehicle to the delivery location to retrieve the package container fromthe delivery location.
 16. The method of claim 15, wherein the thirdtime includes a lock time at which the cover lock is activated by theelectronic controller.
 17. The method of claim 15, further comprising,subsequent to receiving the return request and detecting that the coverhas moved to the closed state, sending the trial end time to a userdevice, the sending of the trial end time corresponding to a request toinitiate sending of the trial end time to the delivery managementserver.
 18. A package container comprising: a body, the body having abase, an opening, and at least one side wall, wherein the base, theopening, and the at least one side wall define a cavity therebetween; acover coupled to the body, the cover movable from a closed statecovering the opening to an open state; a cover lock configured to, whenactivated, keep the cover in the closed state; a user interface; and anelectronic controller coupled to the user interface and the cover lock,the electronic controller including a memory and a processor, whereinthe processor is configured to: store order information in the memory,the order information indicating that the package container is assignedto transport one or more items in the cavity to a delivery location;detect, at a first time, that the cover has moved from the closed stateto the open state; store a trial start time that is based on the firsttime; determine a reminder time based on the trial start time and atrial duration threshold; initiate display of a reminder based on thereminder time, the reminder indicating available time to initiate returnof the one or more items; receive a return request via the userinterface; and based at least in part on receiving the return requestand detecting at a second time that the cover has moved to the closedstate: store a third time as a trial end time, wherein the third time isthe same as or after the second time; determine a trial duration basedon a comparison of the trial start time and the trial end time; andinitiate sending of a transportation request to a delivery managementserver in response to the processor determining that the trial durationis less than or equal to the trial duration threshold, thetransportation request indicating a request to initiate sending of atransportation vehicle to the delivery location to retrieve the packagecontainer from the delivery location.
 19. The package container of claim18, wherein the processor is further configured to, subsequent toreceiving the return request and detecting that the cover has moved tothe closed state, send the trial end time to a user device, the sendingof the trial end time corresponds to a request to initiate sending ofthe trial end time to the delivery management server.
 20. The packagecontainer of claim 18, wherein the processor is further configured toactivate the cover lock subsequent to receiving the return request anddetecting that the cover has moved to the closed state.